A Hybrid Row-Column OLTP Database Architecture for Operational Reporting
نویسندگان
چکیده
Operational reporting differs from informational reporting in that its scope is on day-to-day operations and thus requires data on the detail of individual transactions. It is often not desirable to maintain data on such detailed level in the data warehouse, due to both exploding size of the warehouse and the update frequency required for operational reports. Using an ODS as the source for operational reporting exhibits a similar information latency. In this paper, we propose an OLTP database architecture that serves the conventional OLTP load out of a row-store database and serves operational reporting queries out of a column-store database which holds the subset of the data in the row store required for operational reports. The column store is updated within the transaction of the row database, hence OLTP changes are directly reflected in operational reports. We also propose the virtual cube as a method for consuming operational reports from a conventional warehousing environment. The paper presents the results of a project we did with SAP AG. The described solution for operational reporting has been implemented in SAP Business ByDesign and SAP Business Warehouse.
منابع مشابه
Benchmarking Hybrid OLTP&OLAP Database Systems
Recently, the case has been made for operational or real-time Business Intelligence (BI). As the traditional separation into OLTP database and OLAP data warehouse obviously incurs severe latency disadvantages for operational BI, hybrid OLTP&OLAP database systems are being developed. The advent of the first generation of such hybrid OLTP&OLAP database systems requires means to characterize their...
متن کاملParallel Replication across Formats in SAP HANA for Scaling Out Mixed OLTP/OLAP Workloads
Modern in-memory database systems are facing the need of efficiently supporting mixed workloads of OLTP and OLAP. A conventional approach to this requirement is to rely on ETL-style, application-driven data replication between two very different OLTP and OLAP systems, sacrificing realtime reporting on operational data. An alternative approach is to run OLTP and OLAP workloads in a single machin...
متن کاملHYRISE - A Main Memory Hybrid Storage Engine
In this paper, we describe a main memory hybrid database system called HYRISE, which automatically partitions tables into vertical partitions of varying widths depending on how the columns of the table are accessed. For columns accessed as a part of analytical queries (e.g., via sequential scans), narrow partitions perform better, because, when scanning a single column, cache locality is improv...
متن کاملTowards a One Size Fits All Database Architecture
We propose a new type of database system coined OctopusDB. Our approach suggests a unified, one size fits all data processing architecture for OLTP, OLAP, streaming systems, and scan-oriented database systems. OctopusDB radically departs from existing architectures in the following way: it uses a logical event log as its primary storage structure. To make this approach efficient we introduce th...
متن کاملV+H: Architecture to Manage DSS and OLTP Workloads
In the last few years research has been done in order to define the best approach that DBMSs must follow to manage different workloads. Some approaches have followed the “One size fits all” trying to incorporate all features in a row-oriented DBMS (also called horizontal) to manage both OLTP and DSS workloads. Additionally, there have been specialized DBMS following a columnar approach (also ca...
متن کامل